Repository navigation
docs(ci): title pull requests as conventional commit subjects - #35
Merged
Merged
Conversation
🟢 PR judge · 5 of 5 yes · #35, no linked issue
Checks the script runs itself, 4 of 4 pass
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Pull request titles become conventional commit subjects,
type(scope): summary. The repository squash-merges with the PR title as the commit subject, so the title is whatmain's history shows. AGENTS.md states the rule with its types (feat,fix,perf,refactor,docs,test,ci,build,chore,revert) and scopes (the parts of Nullius), and the/file-issueskill, which assistants use to open PRs, applies it. No check enforces it.Touches
docs and site · CI and skills
Verified
python3 app/tests/parallel.py, OK.Risk
Documentation only; earlier commit subjects on
mainare not rewritten. Undone by a revert.